Without the new option:

With the new --reverse-fields option:

Note that the Field Description order is also influenced by this option, and changes the order as you would expect.

In your screenshot, the reserved space is shown as [low:high] which is inconsistent with the rest. Is that perhaps a typo? It looks odd.

In your screenshot, the reserved space is shown as [low:high] which is inconsistent with the rest. Is that perhaps a typo? It looks odd.

Yep, sorry, I missed that - will fix now.

Also, in the __peakrdl__.py descriptor, can you add a similar option to the cfg_schema to allow users to override it via peakrdl.toml?

Also, in the peakrdl.py descriptor, can you add a similar option to the cfg_schema to allow users to override it via peakrdl.toml?

Sure - will do

@amykyta3 is there an "override convention" in PeakRDL that I should be aware of?

Generally, a command-line option usually overrides a config file option, giving a priority of:

command-line option > config option > default

PeakRDL-html doesn't seem to have any config/command-line options that overlap, but maybe there are other plugins that already set a precedent?

@amykyta3 Please see if you're happy with the committed logic:

• default is False
• if config TOML sets it to be True, and no command-line option is present, it is enabled
• if config TOML sets it to be False, and the command-line option sets it, it is enabled
• if config TOML doesn't set it at all, the command-line option enables it, if present

Looks good! I just committed a slight simplification to the reverse_fields logic. Same thing, just more direct.

Great, thank you, we'll be using this new option immediately :) (well, once released)